Fix audit_log not generated for disruptive actions #175
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR intended to fix issues #170, owasp-modsecurity/ModSecurity/issues/2220 and owasp-modsecurity/ModSecurity/issues/2237 where the audit_log audit_log not generated for disruptive actions.
This changes commit baef88a that fixes the custom error pages issue (owasp-modsecurity/ModSecurity#2143) but it seemed to be returning too early not allowing the audit_logs to be generated on all phases.